sm66 việt nam
sm66 app
tại sm66
sm66 - link nhà cái gsm66.com hà nội
sm66 việt nam
sm66 app
tại sm66
sm66 - link nhà cái gsm66.com hà nội

sm66 com

$5467

Hi SM50 Work Process Overview SM66 System Wide Work Process Overview SM50--Display and Control W

Quantity
Add to wish list
Product description



  Hi

  SM50 Work Process Overview

  SM66 System Wide Work Process Overview

  SM50--Display and Control Work Processes

  Use

  Work processes do the majority of the processing of the SAP System. They execute dialog steps in user transactions, updates, lock administration, etc.

  You can also find the term Work Process in the glossary.

  You can display the current status of the work processes on the application server where you are logged on by choosing Monitor ® System monitoring ® Process overview or Transaction sm50 You must refresh the display to get updated information. The information on this screen is described in the following section.

  The Process overview is intended primarily for information-gathering. For example, you can monitor processes to determine if the number of work processes in your system is adequate, to gather information for trouble-shooting, or for tuning.

  Integration

  By choosing Monitor - System monitoring - Servers, this displays the overview of the SAP application servers. Here, you can further display the work process overview for a particular server in the SAP System by clicking on the desired server name.

  If system load is low and you are displaying the Process overview, you notice that your requests seem to be processed in only one work process. The dispatcher is trying to use one work process for as many dialog steps for one user as possible. This avoids having to reload the roll area for the user

  SM66--Global Work Process Overview

  Purpose

  You can quickly investigate the potential cause of a system performance problem by checking the work process load. You can use the global work process overview to:

  Monitor the work process load on all active instances across the system

  Identify locks in the database (lock waits).

  Using the Global Work Process Overview screen, you can see at a glance:

  The status of each application server

  The reason why it is not running

  Whether it has been restarted

  The CPU and request run time

  The user who has logged on and the client that they logged on to

  The report that is running

  This should clear your doubt. If you need any more clarification you are welcome.

  Regards

  Sumit Jain

  **Reward with points if useful

Related products